💔 -1 overall

This message was automatically generated.

💔 -1 overall

This message was automatically generated.

this makes pretty much sense to me, I quite often find myself simply copy the header from an already existing file, so from now on, I'll copy the correct one :)
let me replay the last test job with a workaround to apply large patches (#423 (comment))
https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/3/

the precommit test is crucial this time even if only comments were changed, because we need to make sure that our checkstyle/spotbugs/etc. think the same about "correct formatting" as us

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/3/console in case of problems.

💔 -1 overall

This message was automatically generated.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/4/console in case of problems.

this makes pretty much sense to me, I quite often find myself simply copy the header from an already existing file, so from now on, I'll copy the correct one :) let me replay the last test job with a workaround to apply large patches (#423 (comment)) https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/3/

the precommit test is crucial even if only comments were changed, because we need to make sure that our checkstyle/spotbugs/etc. think the same about "correct formatting" as us

timeout happened in
https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/3
rerunning as
https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/4

💔 -1 overall

This message was automatically generated.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/5/console in case of problems.

💔 -1 overall

This message was automatically generated.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/6/console in case of problems.

💔 -1 overall

This message was automatically generated.

💔 -1 overall

This message was automatically generated.

Same error I'm getting locally as well when building docker image.

Maybe with latest change in go repo can you please apply the workaround @abstractdog ? I'm not sure where this go is used anyway? I'm thinking of optimizing this dockerfile

💔 -1 overall

This message was automatically generated.

@abstractdog , whenever you have time can you please trigger that workaround one more time?

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/9/console in case of problems.

(!) A patch to the testing environment has been detected. Re-executing against the patched versions to perform further tests. The console is at https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/9/console in case of problems.

replayed as
https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/9
🤞

Thanks for triggering it. The reason why the failures are appearing because dev-support is excluded in jenkinsflile because of this flag:
YETUS_ARGS+=("--skip-dirs=dev-support")

[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.diffplug.spotless:spotless-maven-plugin:3.1.0:check (spotless-check) on project tez-runtime-internals: Execution spotless-check of goal com.diffplug.spotless:spotless-maven-plugin:3.1.0:check failed: Unable to locate file with path: /home/jenkins/jenkins-home/workspace/tez-multibranch_PR-488/src/tez-runtime-internals/dev-support/spotless/license.java: Could not find resource '/home/jenkins/jenkins-home/workspace/tez-multibranch_PR-488/src/tez-runtime-internals/dev-support/spotless/license.java'. -> [Help 1]
[ERROR] 

I have addressed it in #498

Also all these prev failure that's because of rebase issue is yetus behaviour of checking out PR then master branch and then re-applying the commit. This behaviour is also fixed in #498 by using

                    cd "${WORKSPACE}/${SOURCEDIR}"
                    # Ensure origin/master is available for diffing
                    git fetch origin master || true
                    git diff origin/master...HEAD > "${WORKSPACE}/${PATCHDIR}/local-pr.patch"
                    cd "${WORKSPACE}"

@Aggarwal-Raghav : shall we go for #498 first and then come back for this one?

@Aggarwal-Raghav : shall we go for #498 first and then come back for this one?

makes sense

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/10/console in case of problems.

Forgot to fix the -Ptools profile license header 😔

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/11/console in case of problems.

Will take a look at afterwards, the project.root is not resolving correctly. Will eval some plugin to do so.
I'll park it for now and once the other priority PR are merged, will pick it up again.
On bright side, this big PR didn't require the manual workaround in CI to run.

Locally the command is passing 🤔

Will take a look at afterwards, the project.root is not resolving correctly. Will eval some plugin to do so. I'll park it for now and once the other priority PR are merged, will pick it up again. On bright side, this big PR didn't require the manual workaround in CI to run.

Locally the command is passing 🤔

this big PR didn't require the manual workaround in CI to run. <- exactly, already an important step!

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-488/12/console in case of problems.

💔 -1 overall

This message was automatically generated.

The run was aborted because of infra issue 😓

ERROR: Cannot resume build because FlowNode 35 for FlowHead 1 could not be loaded. This is expected to happen when using the PERFORMANCE_OPTIMIZED durability setting and
     Jenkins is not shut down cleanly. Consider investigating to understand if Jenkins was not shut down cleanly or switching to the MAX_SURVIVABILITY durability setting which
     should prevent this issue in most cases